Interfacing with a virtual database system

ABSTRACT

User interactions with a database storage system allow creation of virtual databases based on point-in-time copies associated with a source database. Multiple point-in-time copies are obtained for each source database. A point-in-time copy retrieves data changed in the source database since the retrieval of a previous point-in-time copy. A virtual database (VDB) is created by creating a set of files in the data storage system and mounting the files on a database server allowing the database server to access the files. User interactions allow the user to specify the source database, a point in time associated with the source database and a destination server to create the virtual database. User input can specify other attributes associated with the virtual database including the file paths, database parameters etc. The user can specify schedules of various actions, including making and retention of point-in-time copies.

CROSS REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/894,259 filed on May 14, 2013, which is a continuation of U.S. patentapplication Ser. No. 13/301,448 filed on Nov. 21, 2011, which claims thebenefit of U.S. Provisional Application No. 61/418,396, filed on Nov.30, 2010, each of which is incorporated by reference in its entirety.

BACKGROUND

This invention relates generally to databases and in particular tointerfacing and interacting with storage efficient systems for managingdatabases.

Databases store the data that is critical to an organization and thusform an important part of an organization's information technologyinfrastructure. As the information available in an organization grows,so does the complexity of the infrastructure required to manage thedatabases that store the information. The increased complexity of theinfrastructure increases the resources required to manage the databasesand the applications that depend on the databases. These increased costsmay include the costs associated with hardware for managing thedatabases as well as the costs associated with additional personnelneeded to maintain the hardware. The increased complexity of theinfrastructure also affects the maintenance operations associated withthe databases, for example, causing backup and recovery operations totake significantly longer.

In a typical organization's infrastructure environment, productiondatabase servers run applications that manage the day-to-daytransactions of the organization. Changes to production databases or toapplications that depend on the production databases are tested oncopies of the databases to protect the production environment. Copies ofthe production databases may be required for several stages in thelifecycles of workflows associated with the production database andapplications that depend on the production databases. For example, thestages in the lifecycle of a change incorporated in a productiondatabase may include a development stage, a tuning stage, a testingstage, a quality assurance stage, a certification stage, a trainingstage, and a staging stage. Making copies of the production databasesfor each stage requires redundant and expensive hardware infrastructureas well as the time overhead required to copy the data, which may takedays or weeks. Additional hardware also requires additional costsassociated with physically storing the hardware, such as floor spacerequirements and costs related to power and cooling. Furthermore,redundant hardware typically causes inefficient use of availableresources.

Since databases involve complex manipulations of data and information,database products provide various mechanisms to allow users or databaseadministrators to interact or interface with the database. For example,users and database administrators can interact with the database using auser interface, application programming interface, commands, scripts andthe like. The mechanisms provided by databases for interfacing with thedatabase can be complex since a large number of commands and options forcommands are typically available for manipulating information in adatabase.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent application file contains at least one drawing executed incolor. Copies of this patent application with color drawings will beprovided by the U.S. Patent and Trademark Office upon request andpayment of the necessary fee.

FIG. 1 is diagram illustrating how information is copied from aproduction database to a database storage system and provisioned asvirtual databases using a file sharing system, in accordance with anembodiment of the invention.

FIG. 2 is a schematic diagram of the architecture of a system that makesstorage efficient copies of information from a production database andprovisions virtual databases, in accordance with an embodiment of theinvention.

FIG. 3 shows a process illustrating the steps for interacting with auser for creating a VDB, in accordance with an embodiment.

FIG. 4 shows a user interface for allowing a user to select a sourcedatabase for creating a virtual database, in accordance with anembodiment of the invention.

FIG. 5 shows a user interface for allowing a user to select a particularpoint in time associated with the source database for creating a virtualdatabase based on the selected point in time, in accordance with anembodiment of the invention.

FIG. 6 shows a user interface for allowing a user to select a databaseaction of the source database for creating a virtual database based onthe selected action, in accordance with an embodiment of the invention.

FIG. 7 is a schematic diagram of the architecture of a system that makesstorage efficient copies of information from a production database andprovisions virtual databases, in accordance with an embodiment of theinvention.

FIG. 8A shows a user interface for allowing a user to change parametersassociated with the virtual database being created, in accordance withan embodiment of the invention.

FIG. 8B shows a user interface for allowing the user to specify adatabase name or identifier value for uniquely identifying the virtualdatabase being created, in accordance with an embodiment of theinvention.

FIG. 9 illustrates how database blocks stored on the storage system datastore may be shared by file structures created for different VDBs, inaccordance with an embodiment of the invention.

FIG. 10 shows the user interface for specifying various policiesassociated with entities associated with the database storage system100, in accordance with an embodiment of the invention.

FIG. 11 shows metrics that provide a quantitative measure of storagesavings as a result of use of the database storage system 100, inaccordance with an embodiment of the invention.

FIG. 12 shows performance of the database storage system at variouspoints in time, in accordance with an embodiment of the invention.

FIG. 13 shows the user interface for allowing a user to add a hostserver to the database storage system, in accordance with an embodimentof the invention.

FIG. 14 illustrates an embodiment of a computing machine that can readinstructions from a machine-readable medium and execute the instructionsin a processor or controller.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

Virtual Database Systems

In certain embodiments of the invention, one or more virtual databasesare created based on the state of a production database or a virtualdatabase at a particular point in time, and the virtual databases canthen be individually accessed and modified as desired. A databasecomprises data stored in a computer for use by computer implementedapplications. A database server is a computer program that can interactwith the database and provides database services, for example, access tothe data stored in the database. The virtual database provides efficientstorage of database blocks by efficiently sharing database blocksbetween virtual databases. A database block is a unit of data used by adatabase and comprises a specific number of bytes stored in the storage.A database block can also be referred to as a page. A portion of thedatabase block stores metadata associated with the database block.Examples of information that may be stored in the metadata of a databaseblock include information related to the data stored in the databaseblock, information related to objects of database that the databaseblock is part of, or information indicating when the data in thedatabase block was updated. The information indicating when a databaseblock was updated may be available as a relative ordering of thedatabase blocks based on their time of update.

A database storage system interfaces with a user to receive informationnecessary for creating a virtual database. The database storage systemuses default values as attributes of the virtual database being createdto reduce the burden on the database administrator creating the virtualdatabase. However, the database administrator can chose to specify moreor less information in order to customize the virtual database beingcreated to suit a particular application or purpose.

Database servers include commercially available programs, for example,database servers included with database management systems provided byORACLE, SYBASE, MICROSOFT SQL SERVER, IBM's DB2, MYSQL, and the like.The term “production database” is used in particular examples toillustrate a useful application of the technology; however, it can beappreciated that the techniques disclosed can be used for any database,regardless of whether the database is used as a production database. Thevirtual databases are “virtual” in the sense that the physicalimplementation of the database files is decoupled from the logical useof the database files by a database server.

In one embodiment, information from the production database is copied toa storage system at various times, such as periodically. The schedulefor copying the information from the production database can be either adefault schedule selected by the system or specified by the databaseadministrator. This enables reconstruction of the database filesassociated with the production database for these different points intime. The information may be managed in the storage system in anefficient manner so that copies of information are made only ifnecessary. For example, if a portion of the database is unchanged from aversion that was previously copied, that unchanged portion need not becopied. A virtual database created for a point in time is stored as aset of files that contain the information of the database as availableat that point in time. Each file includes a set of database blocks andthe data structures for referring to the database blocks. In someembodiments, the database blocks may be compressed in order to storethem efficiently.

A virtual database may be created on a database server by creating thedatabase files for the production database corresponding to the state ofthe production database at a previous point in time, as required for thedatabase server. The files corresponding to the virtual database aremade available to the database server using a file sharing mechanism,which links the virtual database to the appropriate database blocksstored on the storage system. The process of making the virtual databaseavailable to a database server is called “provisioning” the virtualdatabase. In some embodiments, provisioning the virtual databaseincludes managing the process of creating a running database serverbased on virtual database. Multiple VDBs can be provisioned based on thestate of the production database at the same point in time. On the otherhand, different VDBs can be based on different point in time state ofthe same production database or different production databases.

The database server on which a virtual database has been provisioned canthen read from and write to the files stored on the storage system. Adatabase block may be shared between different files, each fileassociated with a different VDB. In particular, a database block isshared if the corresponding virtual database systems 130 are onlyreading the information in the database block and not writing to thedatabase block. In one embodiment, the virtual database manager makescopies of the database blocks only if necessary. For example, aparticular database block may be shared by multiple VDBs that read fromthe same database block. But if one of virtual database systems attemptsto write to the database block, a separate copy of the database block ismade because the writing operation causes that database block to bedifferent for the VDB corresponding to that virtual database systemsthan it is for the other VDBs. Systems and methods for creating andusing virtual databases are disclosed in U.S. patent application Ser.No. 12/603,541 filed on Oct. 21, 2009, which is incorporated byreference in its entirety.

System Environment

FIG. 1 illustrates one embodiment for how information may be copied froma production database to a database storage system and provisioned asvirtual databases using a file sharing system. The production databasesystems 110 manage data for an organization. In some embodimentsinformation may be copied from storage level snapshots of productiondatabases or clones of production databases instead of a live productiondatabase. The database storage system 100 retrieves data associated withdatabases from one or more production database systems 110 and storesthe data in an efficient manner, further described below. A databaseadministrator user interface 140 allows a database administrator toperform various actions supported by the database storage system 100.

In response to a request from the administrator system 140, or based ona predefined schedule, the database storage system 100 may send arequest 150 for data to a production database system 110. The productiondatabase system 110 responds by sending information stored in theproduction database as a stream of data 160. The request 150 is sentperiodically and the production database system 110 responds by sendinginformation representing changes of data stored in the productiondatabase since the last response 160 sent by the production databasesystem 110. The database storage system 100 receives the data 160 sentby the production database system 110 and stores the data. The databasestorage system 100 may analyze the data 160 received to determinewhether to store the information or skip the information if theinformation is not useful for reconstructing the database at previoustime points. The database storage system 100 stores the informationefficiently, for example, by keeping versions of database blocks thathave changed and reusing database blocks that have not changed. In anembodiment, database storage system 100 employs a hierarchical cachingsystem where high speed solid-state drive (SSD) or equivalent storagedevices are configured for caching read operations and for persistinglogs for writing operations to magnetic disks.

To create a virtual database, the database storage system 100 createsfiles that represent the information corresponding to the productiondatabase system 110 at a given point in time. The database storagesystem 100 exposes 170 the corresponding files to a virtual databasesystem 130 using a file sharing system 120. The virtual database system130 runs a database server that can operate with the files exposed 170by the database storage system 100. Hence, a virtual copy of theproduction database is created for the virtual database system 130 for agiven point in time in a storage efficient manner.

System Architecture

FIG. 2 shows a high level block diagram illustrating a systemenvironment suitable for making storage efficient copies of informationfrom a production database and provisioning one or more virtualdatabases using that information. The system environment comprises oneor more production database systems 110, a database storage system 100,an administration system 140, and one or more virtual database systems130. Systems shown in FIG. 2 can communicate with each other ifnecessary via a network.

A production database system 110 is typically used by an organizationfor maintaining its daily transactions. For example, an online bookstoremay save all the ongoing transactions related to book purchases, bookreturns, or inventory control in a production system 110. The productionsystem 110 includes a database server 245, a production DB data store250, a vendor interface module 235, and a production system library 285.In alternative configurations, different and/or additional modules canbe included in a production database system 110.

The production DB data store 250 stores data associated with a databasethat may represent for example, information representing dailytransactions of an enterprise. The database server 245 is a computerprogram that provides database services and application programminginterfaces (APIs) for managing data stored on the production DB datastore 250. The production system library 285 provides APIs useful forextracting information from the production database system 110. Thevendor interface module 235 represents APIs provided by a vendor forcustomizing functionality provided by the database server 245, forexample, APIs to retrieve database blocks that changed since a previoustime point. An example of a vendor interface module is the program codeof a database server provided by vendor ORACLE that implements RMANAPIs. Database servers provided by other vendors, for example,MICROSOFT's SQL SERVER or IBM's DB2 have similar APIs. In oneembodiment, the vendor interface module 235 mounts the production DBdata store 250 of the production database system 110 on the databasestorage system 100 using a file sharing system similar to the filesharing system 120. Mounting the production DB data store 250 on thedatabase storage system 100 allows transfer of information stored on theproduction database system 110 to the database storage system 100.

The production system library 285 may be implemented in different waysdepending on the requirements of the vendor interface module 235. In anembodiment, the vendor interface module 235 loads the production systemlibrary 285 in order to call back functions implemented in theproduction system library 285. For example, the production systemlibrary 285 may be a shared object file with a “.so” or a “.DLL” fileextension that contains executable program code that can be called by aC/C++ executable program or by a JAVA program that uses the JAVA NATIVEINTERFACE for interaction with binary code generated by C/C++ programs.Alternatively, the production system library 285 may be implementedusing the JAVA programming language and installed in the productiondatabase system 110 as a file with “.jar” extension. The java programrequires a JAVA VIRTUAL MACHINE running on the production databasesystem 110 for execution. In another embodiment, a part of theproduction system library 285 may be implemented as an executable “.so”shared object file and another part of the production system library 285may be implemented as a JAVA program installed as a “.jar” file.

The vendor interface module 235 responds to requests from databasestorage system 100, and in response to the requests, collects requestedinformation from the production DB data store 250 and returns thecollected information to the database storage system 100. The vendorinterface module 235 may send request to the database server 245 forretrieving information from the production DB data store 250. The vendorinterface module 235 loads the program code in the production systemlibrary 285 and invokes it to transmit the stream of data for to thedatabase storage system 100 for further processing. In some embodimentsthe vendor interface module 235 may directly interact with theproduction DB data store 250 instead of sending a request to thedatabase server 245 to retrieve the necessary database blocks. In otherembodiments, the vendor interface module 235 may retrieve the necessarydatabase blocks from storage level snapshots of production databases orclones of production databases instead of a live production database.

The database storage system 100 retrieves information available in theproduction database systems 110 and stores it. The information retrievedincludes database blocks comprising data stored in the database,transaction log information, metadata information related to thedatabase, information related to users of the database and the like. Theinformation retrieved may also include configuration files associatedwith the databases. For example, databases may use vendor specificconfiguration files to specify various configuration parametersincluding initialization parameters associated with the databases.Copying the configuration files allows a VDB to be created withconfiguration parameters similar to the source production database. Insome embodiments, the configuration parameters files may be modified bya database administrator using the user interface 295 to customize theVDB configuration for a specific usage scenario. For example, theproduction database may be accessed by a database server 245 using aparticular cache size whereas the corresponding VDB may be accessed by adatabase server 260 using a different cache size.

The information retrieved may also include information associated withapplications using the database, for example, an enterprise resourceplanning (ERP) application may be using the database and may have dataspecific to the ERP application. Retrieving the ERP application dataallows a similar ERP application to be executed with a VDB created basedon the production database system. This is beneficial for usagescenarios where a VDB is created for an environment similar to theproduction environment, for example, for testing and development. Adatabase administrator can use the user interface 295 to specify logicfor copying the information that is specific to a production environmentas well as logic for appropriately installing the information with a VDBfor use by a virtual database system 130.

In some embodiments, information regarding users of the productiondatabase, for example, the users with administrative privileges may beobtained by using specific APIs or by running specific scripts on theproduction database. The information about the users can be used tofacilitate life cycle management of VDBs in the system. In anembodiment, a database administrator is allowed to use the userinterface 295 in order to specify information regarding user accounts tobe created and their access permissions. For example, if the VDB iscreated for testing purposes, test users may be created on the VDB fortest organization whereas if the VDB is created as a standby for theproduction database, only users with production support roles shouldhave access. In some embodiments, access permission may specify if auser can provision a privileged VDB. One example of privileged VDB is aVDB with full access to non-public information (information that may notbe accessible to non-privileged users), for example, social securitynumbers or credit card information. The corresponding un-privileged VDBis a VDB with non-public information masked or scrambled. Anotherexample of privileged VDB is a VDB with sensitive data accessibletransparently. The corresponding un-privileged VDB is a VDB withsensitive information encrypted.

In some embodiments, access privileges are simplified to three levels:administrator, owner, and auditor. Administrator has full control of allmanaged objects including databases and hosts. The control available toan administrator included policy management. Owner has access to use ofresources, for example, an owner can provision a VDB. Auditor can viewlogs but may not have rights to consume system resources.

The data stored in the storage system data store 290 can be exposed to avirtual database system 130 allowing the virtual database system 130 totreat the data as a copy of the production database stored in theproduction database system 110. The database storage system 100 includesa point-in-time copy manager 210, a transaction log manager 220, ainterface manager 230, a system configuration manager 215, a storageallocation manager 265, a file sharing manager 270, a virtual databasemanager 275, and a storage system data store 290. In alternativeconfigurations, different and/or additional modules can be included inthe database storage system 100.

The point-in-time copy manager 210 interacts with the productiondatabase system 110 by sending a request to the vendor interface module235 to retrieve information representing a point-in-time copy (alsoreferred to as a “PIT copy”) of a database stored in the production DBdata store 250. The point-in-time copy manager 210 stores the dataobtained from the production database system 110 in the storage systemdata store 290. The data retrieved by the point-in-time copy manager 210corresponds to database blocks (or pages) of the database being copiedfrom the production DB data store 250. After a first PIT copy request toretrieve information production DB data store 250, a subsequent PIT copyrequest may need to retrieve only the data that changed in the databasesince the previous request. The data collected in the first request canbe combined with the data collected in a second request to reconstruct acopy of the database corresponding to a point in time at which the datawas retrieved from the production DB data store 250 for the secondrequest.

The transaction log manager 220 sends request to the production databasesystem 110 for retrieving portions of the transaction logs stored in theproduction database system 110. In some embodiments, the request fromthe transaction log manager 220 is sent to the vendor interface module235. The data obtained by the transaction log manager 220 from thevendor interface module 235 is stored in the storage system data store290. In one embodiment, a request for transaction logs retrieves onlythe changes in the transaction logs in the production database system110 since a previous request for the transaction logs was processed. Thedatabase blocks retrieved by a point in time copy manager 210 combinedwith the transaction logs retrieved by the transaction log manager 220can be used to reconstruct a copy of a database in the production system110 corresponding to times in the past in between the times as whichpoint-in-time copies are made.

The storage allocation manager 265 provides the functionality of savingdata retrieved from the production database system 110. For example, thepoint-in-time copy manager 210 may call APIs of storage allocationmanager to save blocks of data retrieved from the production databasesystem 110. The storage allocation manager 265 keeps track of thevarious versions of each block of data that may be obtained from theproduction database system 110. For a given time point, the storageallocation manager 265 can be requested to provide the latest version ofa block of data obtained before the given time point. The storageallocation manager 265 can also be used for making copies of blocks ofdata. If a block of data is copied for read-only purposes, the storageallocation manager 265 allocates only sufficient storage to keep apointer of reference to the exiting block of data. However, if anattempt to write to the copied block of data is made, the storageallocation manager 265 allocates sufficient storage to make an actualcopy of the block of data to avoid updating the original block of data.

The file sharing manager 270 allows files stored in the storage systemdata store 290 to be shared across computers that may be connected withthe database storage system 100 over the network. The file sharingmanager 270 uses the file sharing system 120 for sharing files. Anexample of a system for sharing files is a network file system (NFS). Asystem for sharing files may utilize fiber channel Storage area networks(FC-SAN) or network attached storage (NAS) or combinations andvariations thereof. The system for sharing files may be based on smallcomputer system interface (SCSI) protocol, internet small computersystem interface (iSCSI) protocol, fiber channel protocols or othersimilar and related protocols. In some embodiments, the database storagesystem 100 may utilize a logical volume manager. Sharing a file storedin the storage system data store 290 using the file sharing manager 270allows a remote computer, for example, the virtual database systems 130to access the data in the shared file. A remote system may be able toread and write from/to the file shared by the storage system data store290. In an embodiment, files are organized in a format emulating a givenfile system disk layout, such as the file system of WINDOWS operatingsystem called NTFS or the UNIX file system (UFS).

The virtual database manager 275 receives requests for creation of avirtual database for a virtual database system 130. The request forcreation of a virtual database may be sent by a database administratorusing the administration system 140 and identifies a production databasesystem 110, a virtual database system 130, and includes a pastpoint-in-time corresponding to which a virtual database needs to becreated. The virtual database manager 275 creates the necessary filescorresponding to the virtual database being created and shares the fileswith the virtual database system 130. The database administrator for avirtual database system 130 may be different from a databaseadministrator for the production database system 110.

The interface manager 230 renders for display information necessary fordisplay using the administration system 140. A database administratoruser can see information available in the storage system data store 290as well as take actions executed by the database storage system. Forexample, a database administrator can see the different productiondatabases stored in the storage system data store 290 obtained fromdifferent production database systems 110. As another example, thedatabase administrator can request the database storage system 100 tomake a PIT copy of a database stored on a production database system 110at a particular point-in-time. In an embodiment, the interface manager230 allows external applications to access information of the databasestorage system 100. For example, the database storage system may provideapplication programming interface (API) to allow third party vendors towrite applications based on database storage system 100. In anembodiment, the interface manager 230 provides web services that allowweb applications to access information available in the database storagesystem 100. For example, the database storage system can be part of acloud computing environment. A third party vendor can use web servicesto implement various workflow scenarios based on VDBs, for example thevarious workflow scenarios described herein. This allows automation ofthe workflow scenarios based on VDBs.

The system configuration manager 215 allows a database administratorusing the administration system 140 to setup or change the configurationof the database storage system 100. For example, when the databasestorage system is being initially setup or at a later stage, the systemconfiguration manager 215 allows a database administrator user or anagent to specify production database systems 110 and virtual databasesystems 130 to connect to. The system configuration manager 215 alsoallows a user with appropriate roles and privileges to setup policiesspecifying the schedule with which the point-in-time copy manager 210retrieves PIT copies of databases in the production database systems 110as well as the frequency and the times at which the transaction logmanager 220 retrieves updates to online transaction logs from theproduction database systems 110. In an embodiment, a schedule canspecify the frequency and times during the day for the PIT and logretrieval actions or it could be an a periodic schedule specifying thecalendar days when the same action should take place.

In an embodiment, policies can be defined by a database administratorand stored in the system configuration manager 215 for variousoperations associated with the loading of point-in-time copies fromproduction database systems 110, loading of transaction logs from theproduction database systems 110, purging of information from thedatabase storage system 100 including point-in-time copies of databasesand transaction log information, and provisioning of virtual databasesystems. A policy specifies rules for executing the specific operation.For example, a policy may specify the operation to be executed based ona predetermined schedule. A policy may determine when to purge PITcopies stored in the database storage system 100 based on number of PITcopies that have been accumulated for a production database. A policymay measure storage availability to determine when to purge information.For example, if the amount of storage available reaches below athreshold level, old PIT copies of selected databases may be purged. Thepolicy may also specify priority of production databases to be usedbefore purging information, for example, low priority databaseinformation is purged before purging high-priority database information.In a particular workflow scenario, a policy may determine when to obtainnew information from a production database and automatically update VDBinformation and provision the updated VDB based on the new information.

A virtual database system 130 includes a database server 260 and a VDBsystem library 280. The database server 260 is similar in functionalityto the database server 245 and is a computer program that providesdatabase services and application programming interfaces (APIs) formanaging data stored on a data store 250. The data managed by thedatabase server 260 may be stored on the storage system data store 290that is shared by the database storage system 100 using a file sharingsystem 120. The VDB system library 280 contains program code forprocessing requests sent by the database storage system 100. Inalternative configurations, different and/or additional modules can beincluded in a virtual database system 130.

FIG. 3 shows a process illustrating the steps for interacting with auser for creating a VDB, in accordance with an embodiment. The databasestorage system 100 receives 305 a request for creation of a VDB. In anembodiment, an access to a uniform resource locator (URL) by the userfor running an application or starting an application by an alternativemechanism may be considered a request for creation of a VDB. Forexample, an application that provides the user interface 295 may providea screen that allows the user to create a VDB upon startup.

The user interface 295 can provide a list of source databases to selectfrom. The user can select a particular source database and send theselection to the database storage system 100. The database storagesystem 100 receives 310 the selection of the source database. The sourcedatabases presented to the user for selection comprise source databasesfor which the database storage system 100 has stored point-in-timecopies and transaction logs. In an embodiment, the user provides inputidentifying a server machine hosting one or more databases. The databasestorage system 100 analyzes the server machine to determine thedatabases hosted by the server machine and presents the discovereddatabases as potential source databases to select from. The discovery ofthe databases can be based on discovery of names of files or file pathsthat are typically used by production database system 110 as well as bydiscovery of processes running on the server machine that are typicallypresent in production database systems 110.

The user interface 295 allows the user to select a point-in-time value.The database storage system 100 receives 315 the selection of thepoint-in-time value. In an embodiment, the user interface 295 presents atime line to the user indicating a range of point-in-time values toselect from, allowing the user to select a point-in-time value byidentifying a position in the time line. The database storage system 100uses the point-in-time value for determining the database blocks of thesource database stored in the storage system data store 290 to be usedfor creating the VDB.

The user interface 295 allows the user to select a destination databasesystem 130 for accessing the VDB being created. The database storagesystem 100 receives 320 the selection of the destination database system130 from the user. In an embodiment, the user interface 295 presents alist of previously selected destination database systems 130 to theuser. Alternatively, the user interface 295 allows the user to enterinformation identifying the destination database systems 130, forexample, using a machine name or internet protocol (IP) address.

The user interface 295 presents 325 to the user, the parameters of thesource database selected by the user. The database storage system 100 bydefault may use values from the parameters of the source database as thecorresponding parameters for the VDB being created. Alternatively, theuser can modify the parameter values presented by the user interface295. The modifications of the parameters are received 325 by thedatabase storage system 100. The database storage system 100 uses theset of parameters including the unmodified values as well as themodified values as the parameters for the VDB being created. In anembodiment the database storage system 100 stores the set of parametersvalues as modified by the user and uses them as the default forsubsequent VDBs created by the user, for example, VDBs created using thesame source database.

The user interface 295 presents 330 to the user, the file paths wherethe database storage system 100 expects to create the files associatedwith the VDB. The user can modify the file paths as well as the filenames. For example, certain applications using the VDB may require aspecial file naming convention or the files to be stored at a particularfile path. The database storage system 100 received 335 themodifications to the file path. In an embodiment, the user interface 295allows the user to map patterns in the default file path to patternsassociated with a desired file path. The mapping of the patterns can bestored by the database storage system 100 and applied to subsequent VDBscreated by the user.

Based on the input received by the database storage system 100 in thesteps described above the database storage system 100 creates the VDB.The created VDB is based on a snapshot and transaction logs associatedwith the point-in-time value selected by the user. The database blocksof the source database associated with updates made in the sourcedatabase prior to the selected point-in-time are linked to a filestructure created for the VDB. The file structure for the VDB is mountedon the destination database system 130, thereby allowing the destinationdatabase system to access the VDB.

In an embodiment, the steps illustrated in the FIG. 3 may be performedby a user or by a script or a program. A user interface may be providedto a user for allowing the user to provide input and execute one or moresteps shown in FIG. 3. Alternatively, a script may perform the varioussteps using commands provided by the database storage system 100 or anapplication may invoke application programming interface (APIs) providedby the database storage system 100 to execute the steps illustrated inFIG. 3. Some of the steps illustrated in the FIG. 3 may be optional andthe database storage system 100 may use default values instead of userprovided values.

FIG. 4 shows a user interface for allowing a user to select a sourcedatabase for creating a virtual database, in accordance with anembodiment of the invention. The user interface shown in FIG. 4 displaysproduction database systems 110 as data sources 420. Each data sourcemay display one or more source databases 410. In an embodiment, a datasource may be selected by default, for example, the last used datasource 420. A data source 420 corresponds to a server and can be addedby the system administrator by specifying information identifying theserver, for example, the host name of the server or the internetprotocol (IP) address of the server along with authenticationinformation. The authentication information is required so that thedatabase storage system 100 is permitted to sent libraries comprisingcode for allowing the database storage system 100 to perform variousactions on the production database system 110.

In response to the user selecting a particular source database 410, theuser interface provides information describing the source databaseincluding its status, size, name etc. as well as information describingthe various point-in-time copies 430 stored on the database storagesystem 100. The information describing each point-in-time copy 430comprises the time at which the point-in-time copy was made, the sourcedatabase from which the point-in-time copy was made, and informationdescribing the source database as well as the production database system110 hosting the source database. The source database can be a virtualdatabase associated with the data source.

The user interface shown in FIG. 4 allows the user to provision 450 anew virtual database based on a selected source database or to export aphysical copy 460 of the selected source database. For example, if thesource database 410 is a virtual database, a physical copy of thedatabase is materialized and stored on a target machine. The userinterface shown in FIG. 4 allows a user to select the target machine 440associated with the virtual database or the physical copy of thedatabase. The target machine 440 can be a virtual database system 130for accessing the virtual database being created.

The user interface shown in FIG. 4 allows a user to organize thedatabases created using groups 470. The attributes of all the databasescan be controlled as a group. For example, policies can be specified forthe entire group including policies defining a schedule for makingpoint-in-time copies of the source database and policies definingretention schedule for point-in-time copies. An attribute specified forthe group 470 is applied by the database storage system 100 to all thedatabases in the group unless the user specifically modifies attributesfor a specific database.

FIG. 5 shows a user interface for allowing a user to select a particularpoint in time associated with the source database for creating a virtualdatabase based on the selected point in time, in accordance with anembodiment of the invention. The point-in-time copies of the sourcedatabase can be taken based on a schedule, for example, once a day.However, the transaction log manager 220 copies transaction logs fromthe source database and stores them on the database storage system 100thereby allowing a virtual database to be created based on a state ofthe source database at a time in between the time of copying of twopoint-in-time copies of the source database. For example, the userselects a point-in-time copy 510 based on a source database 540 forcreation of a virtual database. The user can be presented with a userinterface 520 for selecting a time point after the time of copying ofthe point-in-time copy 510 (and before the time of copying of the nextpoint-in-time copy, if available).

The user interface 520 allowing the user to select a time point inbetween the time of copying of two point-in-time copies can be a timeline marked with various time points that can be selected. The user maybe provided a slider 530 for allowing the selection of a particular timepoint on the time line 520. Alternatively, the user interface canprovide the user with any geometric shape that can be used forrepresenting various time points, for example, a curved line or a thinrectangle or ellipse. The user can select a particular time point byusing a slider 530 or by clicking or double clicking at a particularposition in the geometric shape. In an embodiment the user can bepresented with a list of various time points based on textualrepresentation, for example, a drop down list and the user can make aparticular selection. Another embodiment, allows the user to enter atime value using a data entry widget, for example, text box. The valueentered by the user can be validated by the interface manager 230, forexample, to ensure that the value is within a valid range.

FIG. 6 shows a user interface for allowing a user to select a databaseaction of the source database for creating a virtual database based onthe selected action, in accordance with an embodiment of the invention.A particular time point associated with a database can be determined interms of a sequence provided by the database, for example, a systemchange number. The sequence identifies actions taken by the sourcedatabase and has a monotonically increasing value. For example, everytime a particular type of action is taken by the database, the sequencenumber is updated (i.e., incremented). Examples of actions causing thesequence number to update include commit operations in the databaseassociated with changes to the database including updates, inserts,deletes etc. The sequence number allows the user to select a particularsource database operation for creating a virtual database. The resultingvirtual database is based on the state of the source database up to thepoint in time associated with the selected database operation. Theselection of the sequence value can be based on a geometric shapeassociated with a slider as described for selection of point in time,for example a line 620 such that positions of the line are associatedwith values of the sequence. A particular position of the line can beselected using a slider 630. Alternatively, the sequence value can bemanually entered by a user in a data entry widget or selected from alist, for example, a drop down list.

FIG. 7 illustrates the information obtained at different points in timeby the database storage system 200 from various production databasesystems 110 that is stored in the storage system data store 290. FIG. 7shows information related to two databases, DB1 and DB2 obtained fromthe production database system 110. The information 750 corresponds todata obtained for database DB1 whereas the information 760 correspond tothe data obtained for database DB2. The information 750 or 760 comprisesa set of database blocks and a set of transaction logs. The information750(a) represents the first PIT copy of database DB1 obtained from theproduction database system 110. The information 750(b) represents thefirst transaction log update for the database DB1 since the first PITcopy and the information 750(c) represents the second transaction logupdate for the database DB1 since the first PIT copy. The information750(d) represents second PIT copy of the database DB1. The information750(d) stores only the database blocks that were changed in the databaseDB1 since the first PIT copy was made. The information 750(e) representsthe first transaction log update for the database DB1 since the secondPIT copy. Similarly the information 760 correspond to the database DB2.The time Ti indicated next to a information 750 corresponds to the timethat information was copied in the structure. For a PIT Copy (withoutlog updates, for example, 750(a) or 750(d)) made by a PIT copy manager210, the time Ti represents the time of the last update made to thedatabase blocks before the PIT copy was made. For informationcorresponding to a log update, for example, 750(b), 750(c), or 750(e),the time Ti represents the time of the last transaction log in thecorresponding set of the transactions logs stored.

The arrow 710 shown in FIG. 7 represents the step of creating the filesrepresenting a read/write copy of a database based on the information750 as performed by the virtual database manager 275. The arrows 730represent the step of making the files 770 available to the virtualdatabase system 130 via the file sharing system 120.

FIG. 8 shows a user interface for allowing a user to change parametersassociated with the virtual database being created, in accordance withan embodiment of the invention. The virtual database manager 275 candetermine values for the database parameters of the virtual database.These database parameters determine various attributes associated withthe virtual database, for example, the block size used, attributesdescribing runtime structures created by the virtual database,allocation of memory used for various types of data and structuresassociated with the virtual database, and the like. The databaseparameters values can be based on previous values specified by the user,the database parameter of the source database, information describingthe virtual database system 130 and related information. The userinterface shown in FIG. 8(a) presents the values determined as databaseparameters by the virtual database manager 275 to the user as name-valuepairs 810. The user is allowed to change the parameter values and savethe updated parameters using a button 815. The saved parameter valuescan be applied by the virtual database manager 275 to subsequent virtualdatabases created by the user. In an embodiment, the saved parametervalues are used for subsequent virtual databases created using the samesource database and may be specific to each source database.

The user interface shown in FIG. 8(b) allows the user to specify adatabase name 820 or identifier value for uniquely identifying thevirtual database being created. The user can specify scripts 830comprising instructions to be executed before creating the virtualdatabase and/or scripts 840 comprising instructions to be executed aftercreating the virtual database. The user can also specify file paths ornames for the files used in the file structure created for the virtualdatabase. For example, certain database applications require a specifictype of file structure for the database. The required file structure canbe obtained by the user by specifying the file paths and/or names of thefiles created for the virtual database.

FIG. 9 illustrates how database blocks stored on the storage system datastore 290 may be shared by file structures created for different VDBs.FIG. 9 shows the file structures created for VDBs. As shown in FIG. 9,the block V13 and V14 of the file structure 950(a) point at the latestcopy of the blocks F33 and F34 that are not shared with the VDB files950(b). However, block V11 of VDB files 950(a) shares block F11 withblock U11 of VDB files 1150(b). Similarly block V12 of 950(a) sharesdatabase block F22 with block U12 of 950(b). The sharing of blocksacross multiple VDBs results in efficiently utilization of data storedin the storage system data store 290. In case, one of the VDBs attemptsto write to a shared database block, a copy of the shared database blockis made for the VDB attempting to write. The remaining VDBs that sharedthe database block continue to share the original database block.Accordingly, any changes to the copied database block are not visible tothe remaining VDBs since the changes are specific to the VDB that iswriting to the database block.

A VDB may be created using a point-in-time copy of another VDB as asource. For example, assume VDB1 is created and provisioned to a virtualdatabase system 130. Database blocks associated with the VDB are copiedwhen the virtual database system 130 writes to the database blocks forthe first time. Point-in-time copies of VDB1 are also made based on apredefined schedule. This allows a user to create a second virtualdatabase VDB2 based on a point-in-time copy of VDB1. Transaction logs ofVDB1 are also stored, allowing a user to create the second virtualdatabase VDB2 based on any previous state of VDB1 that may be in-betweenpoint-in-time copies of VDB1.

The virtual database system 130 is allowed to read from the filestructures created for a VDB as well as write to them. When the virtualdatabase system 130 writes to a block Vij, space is allocated for thedatabase block and the data of the corresponding database block copiedto the space allocated. For example, if the virtual database system 130writes to the block V11, space is allocated and block F11 copied to theallocated block. Hence the original copy of the block F11 is maintainedas a read only copy and the virtual database system 130 is allowed towrite to a copy of the appropriate database block created specificallyfor the virtual database system 130. This can be considered a lazymechanism for creating copies of the database blocks that copies adatabase blocks only if the corresponding virtual database system 130writes to the database block. Since the number of blocks that a virtualdatabase system 130 writes to may be a small fraction of the totalnumber of blocks associated with the VDB, the above structure stores thedata associated with the VDB in a highly storage efficient manner. Adatabase block that is not written to by virtual database systems 130may be shared by several virtual database systems without being copiedfor a specific virtual database systems 130.

FIG. 10 shows the user interface for specifying various policiesassociated with entities associated with the database storage system100, in accordance with an embodiment of the invention. These includepolicies associated with source databases, groups of source databases,point-in-time copies of source databases, and virtual databases. Apolicy can specify a schedule for repeating a given action at a specifictime in future or at a periodic interval, for example, at a particulartime every day, or on certain days of the week. For certain long runningtasks, the policy may specify a time interval during which the actionshould be performed. If the action is not completed during the specifiedtime interval, the action is resumed at a subsequent time periodspecified by the schedule. FIG. 10 shows an example schedule 1050 thatperforms or repeats an action during a specific time interval each dayof the week. For example, this time interval may corresponds to a periodwhen the system has low load. This time is preferable for performingtasks that are likely to slow down other operations significantly.

A user can specify policies 1010 for scheduling the operation of theinitial copy of a source database to the database storage system 100.The initial copy of the database can take significant amount of time,depending on the size of the source database. For example, for largesource databases, the initial database copy can take several hours. Theuser can specify policies defining when the initial copy operation isperformed. For example, the user can specify intervals of time when thework load on the database storage system 100 is low, thereby allowingthe database storage system 100 to devote more resources to the databasecopy operation and avoid affecting a large number of other operationsduring the process of copying.

A user can specify policies 1020 describing a schedule for makingpoint-in-time copies of source databases. The source databases caninclude productions databases and virtual databases. The policies 1010may be specified for a group of source databases. A policy specified fora group of source databases is applicable to each source databases,unless overwritten by a policy for a specific source database in thegroup. Since a point-in-time copy takes significantly less time comparedto an initial copy of the source databases, the point-in-time copy canbe performed in one continuous time interval. Accordingly, the schedulefor making point-in-time copies specifies a frequency at which thepoint-in-time copies are made.

FIG. 11 shows metrics that provide a quantitative measure of storagesavings as a result of use of the database storage system 100, inaccordance with an embodiment of the invention. Metrics indicatingstorage savings comprise ratios based on size of storage required forstoring virtual database compared with size of storage required forstoring the same database conventionally (when the virtualizationmechanisms described herein are not utilized). A conventional databasestorage corresponds to a database storage that does not share databaseblocks across multiple virtual databases. The storage required for avirtual database can change over time if updates are performed to thedatabase. Some applications may typically require frequent updateswhereas other applications perform updates less frequently.

The following equation provides a quantitative measure of storagesavings obtained by utilizing a set S of virtual databases.

$\begin{matrix}{{vdbRatio} = \frac{\sum\limits_{S}{db}_{uv}}{\sum\limits_{S}{db}_{v}}} & (1)\end{matrix}$

The metric is called vdbRatio (VDB ratio) and is obtained by taking theratio of size of storage of unvirtualized database (databases storedusing conventional techniques) and the size of storage of virtualdatabases. The variable db_(uv) represents size of storage of anunvirtualized database. The symbol

$\sum\limits_{S}$indicates summation of a parameter associated with each database, thesummation computed over all databases belonging to a set S of databases.The variable db_(v) represents size of storage occupied by a virtualizeddatabase.

The following equation provides a quantitative measure of storagesavings provided by the information stored in the database storagesystem 100 based on the mechanisms described herein, for example, as aresult of reusing database blocks across point-in-time copies of sourcedatabases.

$\begin{matrix}{{timeFlowRatio} = \frac{{\sum\limits_{S}{dSource}_{uv}} + {\sum\limits_{S}{SS}_{uv}} + {\sum\limits_{S}{{db}\;{Log}_{uv}}}}{{\sum\limits_{S}{dSource}_{v}} + {\sum\limits_{S}{SS}_{v}} + {\sum\limits_{S}{{db}\;{Log}_{v}}}}} & (2)\end{matrix}$

The metric determined using equation (2) is called timeFlowRatio(time-flow ratio). The symbol

$\sum\limits_{S}$indicates summation of a parameter associated with each database, thesummation computed over all databases belonging to a set S of databases.The variable dSource_(v) represents the size of the storage occupied bythe data blocks obtained initially from each source database. Thevariable SS_(v) represents size of storage occupied by eachpoint-in-time copy obtained from the source database stored invirtualized form such that database blocks that do not change betweentwo consecutive point-in-time copies are shared. The variable dbLog_(v)represents size of storage occupied by the database logs obtained fromthe source database from a given point in time stored in virtualizedform. The dSource_(uv), SS_(uv), and dbLog_(uv) corresponds to the abovesize of the storage occupied by the data blocks obtained initially, sizeof storage occupied by each point-in-time copy, and size of storageoccupied by the database logs corresponding to each database when theinformation is stored in unvirtualized form. In an embodiment, thevariables dSource_(uv), SS_(uv), and dbLog_(uv) represent the size ofthe corresponding information as the source database stores it, assumingthe source database is a conventional database and not a virtualdatabase.

Other variations of the metric indicated in equations (1) and (2) can beused, for example, the inverse of the ration can be used or the twovalues corresponding to the numerator and denominator presentedseparately. FIG. 11 illustrates how the VDB ratio 1120 and the time-flowratio 1110 can be presented to a user in graphical form. As shown inFIG. 11, geometric shapes represent the numerator and the denominatorvalues such that the size of the geometric shape corresponds to thevalue represented. As shown in FIG. 11, the geometric shapes arerectangular but could be other shapes, for example, circular orelliptical.

FIG. 12 shows the metrics indicating performance of the database storagesystem at various points in time, in accordance with an embodiment ofthe invention. The x-axis 1220 displays the time for which theperformance of the database storage system is presented and the graphs1210 along the y-axis 1230 indicate the performance. Each graph 1210corresponds to a current task that is active.

FIG. 13 shows the user interface for allowing a user to add a hostserver to the database storage system, in accordance with an embodimentof the invention. This user interface can be used to add a host serverthat acts as a production database systems 110 as well as virtualdatabase system 130. The user provides information 1310 identifying thehost server including the host name and/or host address, andauthentication information required for accessing the host serverincluding the login and password. The authentication information allowsthe database storage system 100 to access the host server in order toinstall program code on the host server and to be able to accessinformation from the host server, for example, from source databases.The user interface can also allow the user to specify a toolkit paththat specifies where the program code is installed on the host server.

Computing Machine Architecture

FIG. 14 is a block diagram illustrating components of an example machineable to read instructions from a machine-readable medium and executethem in a processor (or controller). Specifically, FIG. 14 shows adiagrammatic representation of a machine in the example form of acomputer system 1400 within which instructions 1424 (e.g., software) forcausing the machine to perform any one or more of the methodologiesdiscussed herein may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a set-top box (STB), a personal digitalassistant (PDA), a cellular telephone, a smartphone, a web appliance, anetwork router, switch or bridge, or any machine capable of executinginstructions 1424 (sequential or otherwise) that specify actions to betaken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute instructions1424 to perform any one or more of the methodologies discussed herein.

The example computer system 1400 includes a processor 1402 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), adigital signal processor (DSP), one or more application specificintegrated circuits (ASICs), one or more radio-frequency integratedcircuits (RFICs), or any combination of these), a main memory 1404, anda static memory 1406, which are configured to communicate with eachother via a bus 1408. The computer system 1400 may further includegraphics display unit 1410 (e.g., a plasma display panel (PDP), a liquidcrystal display (LCD), a projector, or a cathode ray tube (CRT)). Thecomputer system 1400 may also include alphanumeric input device 1412(e.g., a keyboard), a cursor control device 1414 (e.g., a mouse, atrackball, a joystick, a motion sensor, or other pointing instrument), astorage unit 1416, a signal generation device 1418 (e.g., a speaker),and a network interface device 1420, which also are configured tocommunicate via the bus 1408.

The storage unit 1416 includes a machine-readable medium 1422 on whichis stored instructions 1424 (e.g., software) embodying any one or moreof the methodologies or functions described herein. The instructions1424 (e.g., software) may also reside, completely or at least partially,within the main memory 1404 or within the processor 1402 (e.g., within aprocessor's cache memory) during execution thereof by the computersystem 1400, the main memory 1404 and the processor 1402 alsoconstituting machine-readable media. The instructions 1424 (e.g.,software) may be transmitted or received over a network 1426 via thenetwork interface device 1420.

While machine-readable medium 1422 is shown in an example embodiment tobe a single medium, the term “machine-readable medium” should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions (e.g., instructions 1424). The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring instructions (e.g., instructions 1424) for execution by themachine and that cause the machine to perform any one or more of themethodologies disclosed herein. The term “machine-readable medium”includes, but not be limited to, data repositories in the form ofsolid-state memories, optical media, and magnetic media.

Additional Configuration Considerations

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a tangible computer readable storage medium or any typeof media suitable for storing electronic instructions, and coupled to acomputer system bus. Furthermore, any computing systems referred to inthe specification may include a single processor or may be architecturesemploying multiple processor designs for increased computing capability.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

The invention claimed is:
 1. A method of creating a virtual databasesystem, the method comprising: storing, by a database storage system,point-in-time copies of one or more source databases, wherein each ofthe one or more source databases stores metadata describing data storedin the source database, wherein a point-in-time copy of a given sourcedatabase stored in the database storage system comprises one or moredatabase blocks associated with multiple point-in-time copies of thegiven source database, wherein information stored in a database blockcomprises metadata associated with the database block; configuring forpresentation, by the database storage system, one or more userinterfaces for receiving a request for creating a virtual database, theone or more user interfaces configured to receive: informationidentifying a source database from the one or more source databases,information identifying a point in time associated with the sourcedatabase, and information identifying a destination database server foraccessing the virtual database being created; receiving, from the one ormore user interfaces, information identifying a particular sourcedatabase for the virtual database being created; receiving, from the oneor more user interfaces, information identifying a particular point intime associated with the particular source database; receiving, from theone or more user interfaces, information identifying a particulardestination database server for accessing the virtual database beingcreated; creating the virtual database on the database storage system,wherein the created virtual database stores data corresponding to astate of the particular source database, the state associated with theparticular point in time, wherein the created virtual database sharesdatabase blocks with one or more other virtual databases stored in thedatabase storage system; and providing access to the particulardestination database server, the access for allowing the particulardestination database server to perform read and write operations on thecreated virtual database.
 2. The method of claim 1, wherein metadataassociated with the database block comprises information indicating atime of update of data of the database block.
 3. The method of claim 1,wherein metadata associated with the database block comprisesinformation related to the data stored in the database block.
 4. Themethod of claim 1, wherein metadata associated with the database blockcomprises information related to one or more objects of a database thatthe database block is part of.
 5. The method of claim 1, wherein theparticular source database is one of: a live production database; astorage level snapshot of a production database; a clone of a productiondatabase; or a previously created virtual database.
 6. The method ofclaim 1, wherein the one or more user interfaces are configured topresent a list of potential destination database servers, whereinreceiving information identifying the destination database servercomprises receiving a selection of the destination database server fromthe list of potential destination database servers presented via the oneor more user interfaces.
 7. The method of claim 1, wherein the one ormore user interfaces are configured to present a list of potentialsource databases, and wherein receiving information identifying thesource database comprises receiving a selection of the source databasefrom the list of potential source databases presented via the one ormore user interfaces.
 8. The method of claim 1, wherein the one or moreuser interfaces are configured to receive a selection of a host serverand wherein information identifying the particular source database isreceived responsive to: receiving, from the one or more user interfaces,selection of a particular host server associated with the particularsource database; discovering databases installed on the particular hostserver; and sending for presentation via the one or more userinterfaces, information describing the discovered databases forselection of a discovered database to be used as the particular sourcedatabase.
 9. The method of claim 1, wherein the one or more userinterfaces are configured to present a geometric shape, whereinpositions in the geometric shape correspond to a time value, and whereinreceiving information identifying a point in time comprises: receiving aselection of a position in the geometric shape; and mapping theselection of the position in the geometric shape to the identified pointin time.
 10. The method of claim 1, wherein the one or more userinterfaces are configured to present a geometric shape, whereinpositions in the geometric shape correspond to database operations inthe source database and wherein receiving the information identifyingthe point in time comprises: receiving a selection of a position in thegeometric shape; mapping the selection of the position in the geometricshape to a database operation performed in the source database; anddetermining the identified point in time based on a time of execution ofthe database operation.
 11. The method of claim 1, wherein the one ormore user interfaces are configured to present a set of databaseparameters for the virtual database being created, the method furthercomprising: receiving, from the one or more user interfaces,modifications to one or more database parameters from the set ofdatabase parameters to obtain a modified set of database parameters; andusing the modified set of database parameters for creating the virtualdatabase.
 12. The method of claim 11, further comprising: storing themodified set of database parameters for creating subsequent virtualdatabases; and using the modified set of parameters for creating asecond virtual database.
 13. The method of claim 1, wherein informationidentifying the particular destination database server comprises one ofa machine name or internet protocol address.
 14. The method of claim 1,further comprising: configuring for presentation a user interface forspecifying a group of virtual databases wherein an attribute specifiedfor the group is applied to all the virtual databases in the group. 15.A non-transitory computer readable storage medium storing instructionsfor: storing, by a database storage system, point-in-time copies of oneor more source databases, wherein each of the one or more sourcedatabases stores metadata describing data stored in the source database,wherein a point-in-time copy of a given source database stored in thedatabase storage system comprises one or more database blocks associatedwith multiple point-in-time copies of the given source database, whereininformation stored in a database block comprises metadata associatedwith the database block; configuring for presentation, by the databasestorage system, one or more user interfaces for receiving a request forcreating a virtual database, the one or more user interfaces configuredto receive: information identifying a source database from the one ormore source databases, information identifying a point in timeassociated with the source database, and information identifying adestination database server for accessing the virtual database beingcreated; receiving, from the one or more user interfaces, informationidentifying a particular source database for the virtual database beingcreated; receiving, from the one or more user interfaces, informationidentifying a particular point in time associated with the particularsource database; receiving, from the one or more user interfaces,information identifying a particular destination database server foraccessing the virtual database being created; creating the virtualdatabase on the database storage system, wherein the created virtualdatabase stores data corresponding to a state of the particular sourcedatabase, the state associated with the particular point in time,wherein the created virtual database shares database blocks with one ormore other virtual databases stored in the database storage system; andproviding access to the particular destination database server, theaccess for allowing the particular destination database server toperform read and write operations on the created virtual database. 16.The non-transitory computer readable storage medium of claim 15, whereinmetadata associated with the database block comprises one or more of:information indicating a time of update of data of the database block;information related to the data stored in the database block; andinformation related to one or more objects of a database that thedatabase block is part of.
 17. The non-transitory computer readablestorage medium of claim 15, wherein the particular source database isone of: a live production database; a storage level snapshot of aproduction database; a clone of a production database; or a previouslycreated virtual database.
 18. The non-transitory computer readablestorage medium of claim 15, wherein the one or more user interfaces areconfigured to present a list of potential destination database servers,wherein receiving information identifying the destination databaseserver comprises receiving a selection of the destination databaseserver from the list of potential destination database servers presentedvia the one or more user interfaces.
 19. The non-transitory computerreadable storage medium of claim 15, wherein the one or more userinterfaces are configured to present a list of potential sourcedatabases, and wherein receiving information identifying the sourcedatabase comprises receiving a selection of the source database from thelist of potential source databases presented via the one or more userinterfaces.
 20. The non-transitory computer readable storage medium ofclaim 15, wherein the one or more user interfaces are configured toreceive a selection of a host server and wherein information identifyingthe particular source database is received responsive to: receiving,from the one or more user interfaces, selection of a particular hostserver associated with the particular source database; discoveringdatabases installed on the particular host server; and sending forpresentation via the one or more user interfaces, information describingthe discovered databases for selection of a discovered database to beused as the particular source database.
 21. The non-transitory computerreadable storage medium of claim 15, wherein the one or more userinterfaces are configured to present a geometric shape, whereinpositions in the geometric shape correspond to a time value, and whereinreceiving information identifying a point in time comprises: receiving aselection of a position in the geometric shape; and mapping theselection of the position in the geometric shape to the identified pointin time.
 22. The non-transitory computer readable storage medium ofclaim 15, wherein the one or more user interfaces are configured topresent a geometric shape, wherein positions in the geometric shapecorrespond to database operations in the source database and whereinreceiving the information identifying the point in time comprises:receiving a selection of a position in the geometric shape; mapping theselection of the position in the geometric shape to a database operationperformed in the source database; and determining the identified pointin time based on a time of execution of the database operation.
 23. Thenon-transitory computer readable storage medium of claim 15, wherein theone or more user interfaces are configured to present a set of databaseparameters for the virtual database being created, the non-transitorycomputer readable storage medium further storing instructions for:receiving, from the one or more user interfaces, modifications to one ormore database parameters from the set of database parameters to obtain amodified set of database parameters; and using the modified set ofdatabase parameters for creating the virtual database.
 24. Thenon-transitory computer readable storage medium of claim 23, furtherstoring instructions for: storing the modified set of databaseparameters for creating subsequent virtual databases; and using themodified set of parameters for creating a second virtual database. 25.The non-transitory computer readable storage medium of claim 15, whereininformation identifying the particular destination database servercomprises one of a machine name or internet protocol address.
 26. Thenon-transitory computer readable storage medium of claim 15, furtherstoring instructions for: configuring for presentation a user interfacefor specifying a group of virtual databases wherein an attributespecified for the group is applied to all the virtual databases in thegroup.
 27. The non-transitory computer readable storage medium of claim15, wherein metadata associated with the database block comprisesinformation indicating a time of update of data of the database block.28. The non-transitory computer readable storage medium of claim 15,wherein metadata associated with the database block comprisesinformation related to the data stored in the database block.
 29. Thenon-transitory computer readable storage medium of claim 15, whereinmetadata associated with the database block comprises informationrelated to one or more objects of a database that the database block ispart of.
 30. A computer system comprising: an electronic processor; anda non-transitory computer readable storage medium for storinginstructions for: storing, by a database storage system, point-in-timecopies of one or more source databases, wherein each of the one or moresource databases stores metadata describing data stored in the sourcedatabase, wherein a point-in-time copy of a given source database storedin the database storage system comprises one or more database blocksassociated with multiple point-in-time copies of the given sourcedatabase, wherein information stored in a database block comprisesmetadata associated with the database block; configuring forpresentation, by the database storage system, one or more userinterfaces for receiving a request for creating a virtual database, theone or more user interfaces configured to receive: informationidentifying a source database from the one or more source databases,information identifying a point in time associated with the sourcedatabase, and information identifying a destination database server foraccessing the virtual database being created; receiving, from the one ormore user interfaces, information identifying a particular sourcedatabase for the virtual database being created; receiving, from the oneor more user interfaces, information identifying a particular point intime associated with the particular source database; receiving, from theone or more user interfaces, information identifying a particulardestination database server for accessing the virtual database beingcreated; creating the virtual database on the database storage system,wherein the created virtual database stores data corresponding to astate of the particular source database, the state associated with theparticular point in time, wherein the created virtual database sharesdatabase blocks with one or more other virtual databases stored in thedatabase storage system; and providing access to the particulardestination database server, the access for allowing the particulardestination database server to perform read and write operations on thecreated virtual database.
 31. The computer system of claim 30, whereinmetadata associated with the database block comprises one or more of:information indicating a time of update of data of the database block;information related to the data stored in the database block; andinformation related to one or more objects of a database that thedatabase block is part of.
 32. The computer system of claim 30, whereinthe particular source database is one of: a live production database; astorage level snapshot of a production database; a clone of a productiondatabase; or a previously created virtual database.
 33. The computersystem of claim 30, wherein the one or more user interfaces areconfigured to present a list of potential destination database servers,wherein receiving information identifying the destination databaseserver comprises receiving a selection of the destination databaseserver from the list of potential destination database servers presentedvia the one or more user interfaces.
 34. The computer system of claim30, wherein the one or more user interfaces are configured to present alist of potential source databases, and wherein receiving informationidentifying the source database comprises receiving a selection of thesource database from the list of potential source databases presentedvia the one or more user interfaces.
 35. The computer system of claim30, wherein the one or more user interfaces are configured to receive aselection of a host server and wherein information identifying theparticular source database is received responsive to: receiving, fromthe one or more user interfaces, selection of a particular host serverassociated with the particular source database; discovering databasesinstalled on the particular host server; and sending for presentationvia the one or more user interfaces, information describing thediscovered databases for selection of a discovered database to be usedas the particular source database.
 36. The computer system of claim 30,wherein the one or more user interfaces are configured to present ageometric shape, wherein positions in the geometric shape correspond toa time value, and wherein receiving information identifying a point intime comprises: receiving a selection of a position in the geometricshape; and mapping the selection of the position in the geometric shapeto the identified point in time.
 37. The computer system of claim 30,wherein the one or more user interfaces are configured to present ageometric shape, wherein positions in the geometric shape correspond todatabase operations in the source database and wherein receiving theinformation identifying the point in time comprises: receiving aselection of a position in the geometric shape; mapping the selection ofthe position in the geometric shape to a database operation performed inthe source database; and determining the identified point in time basedon a time of execution of the database operation.
 38. The computersystem of claim 30, wherein the one or more user interfaces areconfigured to present a set of database parameters for the virtualdatabase being created, wherein the non-transitory computer readablestorage medium further stores instructions for: receiving, from the oneor more user interfaces, modifications to one or more databaseparameters from the set of database parameters to obtain a modified setof database parameters; and using the modified set of databaseparameters for creating the virtual database.
 39. The computer system ofclaim 38, wherein the non-transitory computer readable storage mediumfurther stores instructions for: storing the modified set of databaseparameters for creating subsequent virtual databases; and using themodified set of parameters for creating a second virtual database. 40.The computer system of claim 30, wherein information identifying theparticular destination database server comprises one of a machine nameor internet protocol address.
 41. The computer system of claim 30,wherein the non-transitory computer readable storage medium furtherstores instructions for: configuring for presentation a user interfacefor specifying a group of virtual databases wherein an attributespecified for the group is applied to all the virtual databases in thegroup.
 42. The computer system of claim 30, wherein metadata associatedwith the database block comprises information indicating a time ofupdate of data of the database block.
 43. The computer system of claim30, wherein metadata associated with the database block comprisesinformation related to the data stored in the database block.
 44. Thecomputer system of claim 30, wherein metadata associated with thedatabase block comprises information related to one or more objects of adatabase that the database block is part of.